Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1588

reference
293-tree-1
name
1588
tree-preservation-order

undefined

293-tpo-1
uprn
address-text
point
POINT (-1.040858 50.897850)
geometry
MULTIPOLYGON (((-1.040787 50.897843,-1.040790 50.897857,-1.040800 50.897869,-1.040816 50.897879,-1.040835 50.897886,-1.040857 50.897888,-1.040879 50.897886,-1.040899 50.897880,-1.040915 50.897870,-1.040925 50.897858,-1.040929 50.897844,-1.040926 50.897830,-1.040916 50.897817,-1.040901 50.897807,-1.040881 50.897801,-1.040859 50.897798,-1.040837 50.897800,-1.040817 50.897807,-1.040801 50.897817,-1.040791 50.897829,-1.040787 50.897843)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL